The Experian, Equifax and TransUnion connectors have been updated to support CreditSharp version 2019.16 in Temenos Infinity. This version includes the following updates to credit processing:

• The annual refresh of the Risk Based Pricing lookup tables has been applied, which allows the relative score rank and percentile values for eligible bureau score models to be appended when not provided in a credit bureau response.
• The following updates have been made for Equifax:
  • Equifax now fully supports score attribute products ADA (model id 05127) CMA (model id 01191).
  • Equifax has updated the naming convention of their Equifax Pinnacle score models to FICO Next Gen.
  • Equifax has updated their responses to accommodate their upcoming Employment data change, which moves from the use of dates Hired and Verified to First and Last Reported date. As of February 1, 2020, Employment date fields are directed to the CreditSharp values "FirstReported" and "LastReported." 
• As a result of Equifax's change to Employment data, Date Left (or Employee Termination Date) is no longer populated by any credit bureau. The Employment Information section of a report now includes "First Rptd" and "Last Rptd" in each layout.  
• Equifax and TransUnion inquiries can now include requests for score models that have not been included in known CreditSharp model definitions. If an attempt is made to submit an inquiry using an unknown score model id, CreditSharp does not allow the request to proceed, and returns an error. Now, if it is necessary to submit a request using an existing score model that has not been defined within CreditSharp, the validation error can be suppressed by preceding the model id with an exclamation point. For example, EquifaxRequest.AddModel("!08888").

For more information on the above updates, please contact the applicable credit bureau.

Temenos Infinity's Account Origination module now supports the DataSafe – Origination connector. Prior to this enhancement, the Fiserv DataSafe core only supported the ability to use the Loan Origination module in the DataSafe interface. Now, institutions are able to use both the Loan Origination and Account Origination modules in DataSafe. Through standard Temenos mapping, and customizable Import and Disbursement values, Temenos Infinity's DataSafe Origination connector shares a read/write relationship with the DataSafe core that now supports the ability to render an account decision in an application, as well as create and fund new account products in DataSafe.

For more information, please see the DataSafe connector guide and Account Origination field mapping document.

The ChexSystems connector has been enhanced to support the FIS Applicant Closure Reason panel at both the Applicant and Application level. Prior to this enhancement, this panel was only available to add to Applicant screens. Now, the FIS Application Closure Reason panel has been added to the Origination Screen Designer to allow institutions to populate account closure data from a Qualifile® report within an Application screen for each applicant on an application. This panel displays the same data as the FIS Applicant Closure Reasons panel, but includes a grouping in the grid for each applicant who has one or more closures reported by Qualifile®.

For more information, please see the Using the Connector topic in the ChexSystems connector guide.

The FIS ChexSystems® connector has been enhanced with the ability to request OFAC screenings within the QualiFile® report. Prior to this enhancement, the users were unable to include OFAC screenings as part of the QualiFile® report. To support this functionality, the QualiFile® Report section in the System Management > Connectors > FIS > ChexSystems® page has been enhanced with a new parameter, Include OFAC. When selected, this parameter automatically includes an OFAC check within all QualiFile® report requests. Additionally, the OFAC response is now displayed in a new OFAC Indicator column added to the QualiFile® panel.

OFAC is a billable service in ChexSystems®.

The FIS ChexSystems® connector has also been enhanced with the ability to present the product offers returned within a QualiFile® report as cross-sell opportunities to applicants. Prior to this enhancement, these product offerings were returned within the QualiFile® report; however, the FIS ChexSystems® connector did not support the ability to present the opportunities to applicants. To support this enhancement, a new Application panel, QualiFile® Product Offerings, has been added to System Management > Origination > Screens, which has the ability to present up to 10 of the QualiFile® product offerings in Temenos Infinity. Additionally, institutions also now have the ability to author CrossSell Product Rules that automatically present the product offerings to applicants as cross-sells.

For more information on these enhancements, please see the FIS ChexSystems® Connector Guide.

The DataSafe Origination interface has been enhanced to send the SQL queries for Applicant Import using Fiserv ConnectIT. Prior to this enhancement, queries for Applicant Import were sent through the ODBC driver. Now, Fiserv has deprecated the ability to send SQL queries through a VPN for Applicant Import; therefore, the DataSafe interface has been updated to send the current SQL queries through HTTP using Fiserv ConnectIT. Additionally, since an ODBC configuration is no longer required, the section for DataSafe/SQL Parameters has been removed from the DataSafe connector page.

For more information, please see the Activating the Connector topic in the DataSafe Origination connector guide.

The DNA interface has been enhanced to support the ability to overwrite the liability payment amount set during Applicant Import. Prior to this enhancement, the CurrPmtAmt field was used to populate the payment amount for a liability, and institutions were unable to override the value. Now, the Account.LoanBalances.RegularPaymentAmount field has been updated to support a host value in the Account Detail Inquiry request, which provides the ability to override the value of the CurrPmtAmt for an internal liability during Applicant Import.

When the Accounts.Account.CurreAcctStatCd.MjAcctypCd field is set to CML, CNS, or MTG for an internal liability during Applicant Import, the Account Detail Inquiry request is now sent to DNA. If a host value is written for Account.LoanBalances.RegularPaymentAmount, the value is used to populate the Temenos Application > Liability > Payment Amount field, rather than the CurrPmtAmt.

For more information, please see the Account Detail Inquiry and Get Host Applicant tabs in the DNA Field Mapping document.

Temenos Infinity has been enhanced to maintain the credit lock placed on a report during credit processing. Prior to this enhancement, when credit was pulled through an event/action pair, there was a small gap of time between the credit lock being released and the data from the credit report being saved to the database. This allowed for credit to be pulled more than once, which resulted in errors due to simultaneous credit pulls. Now, when an event/action pair executes to pull credit, and/or an application is decisioned, the system has been updated to ensure that a lock on a credit report is maintained until the data from the report is saved to the database.

To support this, a Save step has been added to the credit report process, which occurs when pulling credit through event processing to ensure that credit data is immediately saved to the database after credit report parsing and deduping has occurred. The system has also been updated to maintain the credit lock through the above save process. During decisioning, the system also now checks to see if there is a credit report in use and locked, and, if there is, the system waits until the lock is released to proceed with the decisioning process.

For more information on credit processing, please see the Pulling Credit topic in the User Guide.

The Update From Core Action has been enhanced to allow institutions to specify which applicant demographic fields are updated from the core when the action executes. Prior to this enhancement, institutions were able to specify the segments included in the Update From Core action, but could not determine specific fields that were updated with the action. Now, when Include Demographics is selected for the Update from Core action, a list of Applicant Demographic fields populates in the Edit Action window to provide the ability to select the specific demographics to be updated with the action. By default, all of the demographic fields are selected; however, administrators can select and clear the check box next to each field as desired.

If Include Demographics is selected for the Upgrade from Core action prior to the 20.00 upgrade, all Applicant Demographics are automatically selected for the action after the upgrade.

For more information on this functionality, and a list of the Applicant Demographics that can be updated with the Update from Core action, please see the Origination Actions section of the Event Processing topic in the Administrator guide.

Temenos Infinity has been enhanced to include 25 new Liability level fields, and two new Application level fields, which support the ability to populate additional credit card information from the core.

The new Liability level fields have been added to the Field List for rules, reports and views, and have also been made available in the Field Selector for the Liabilities Panel in both Virtual Capture and Temenos Infinity.

The two new Application fields, Application > Statement Group and Application > Statement Mail Code, have been added to the Field List for Application screens, rules, reports, and views, as well as to the Fields tab in System Management > Origination > Editability.

For institutions on the Symitar core: New fields have been added to the following Symitar PowerOns to support the ability to import values for the new Liability and Application level fields added with this feature:

• AKSW.DEMOGRAPHIC
• AKSW.LOANSHARE
• AKSW.GETACCOUNT

The Symitar GetAccountDemographics, GetAccountLiabilities, CreateLoanRecord, and CreateLoanNameRecord calls have also been updated to support the ability to direct map and/or override the new field values being imported from, or disbursed to Symitar during the application process.

For an overview of the fields added to each Symitar PowerOn, please see the Core Enhancements topic in the 20.00 Release Highlights. For more information on the fields added to each Symitar call, please see the Symitar Field Mapping document.

The Origination modules have been enhanced to make vendor data available for Product Selection rules. Prior to this enhancement, vendor fields were not available to be used within Product Selection rules. Through this enhancement, vendor data has been made available for Product Selection rules, which provides financial institutions the ability to use the following vendor fields to determine the correct product for an application:

• Application > Vendor > Address > Address1
• Application > Vendor > Address > Address2
• Application > Vendor > Address > Address3
• Application > Vendor > Address > Address Category Id
• Application > Vendor > Address > Address Status Id
• Application > Vendor > Address > Address Type Id
• Application > Vendor > Address > City
• Application > Vendor > Address > Classification Id
• Application > Vendor > Address > Country Id
• Application > Vendor > Address > End Date
• Application > Vendor > Address > Host Values > Field1
• Application > Vendor > Address > Host Values > Field2
• Application > Vendor > Address > Host Values > Field3
• Application > Vendor > Address > Host Values > Field4
• Application > Vendor > Address > Host Values > Field5
• Application > Vendor > Address > Host Values > Value
• Application > Vendor > Address > Housing Loan Balance Amount
• Application > Vendor > Address > Is Total Monthly Expense
• Application > Vendor > Address > Length at Address
• Application > Vendor > Address > Monthly Expense Amount
• Application > Vendor > Address > Postal Code
• Application > Vendor > Address > Start Date
• Application > Vendor > Address > State Code
• Application > Vendor > Address > State Id
• Application > Vendor > Address > Township
• Application > Vendor > Address > Township Id
• Application > Vendor > Annual Review Date
• Application > Vendor > Approve Credit Limit
• Application > Vendor > Business Credit Report Date
• Application > Vendor > Channel Id
• Application > Vendor > Channel Status
• Application > Vendor > Channel Status Id
• Application > Vendor > Code
• Application > Vendor > Created By Id
• Application > Vendor > Created Date
• Application > Vendor > Email Address
• Application > Vendor > Fax > Extension
• Application > Vendor > Fax > Host Values > Field1
• Application > Vendor > Fax > Host Values > Field2
• Application > Vendor > Fax > Host Values > Field3
• Application > Vendor > Fax > Host Values > Field4
• Application > Vendor > Fax > Host Values > Field5
• Application > Vendor > Fax > Host Values > Value
• Application > Vendor > Fax > Phone Number
• Application > Vendor > Fax > Phone Type Id
• Application > Vendor > Identity Number
• Application > Vendor > Inception Date
• Application > Vendor > Is Active
• Application > Vendor > Last Application Date
• Application > Vendor > Last Booked Date
• Application > Vendor > Last Review Date
• Application > Vendor > Last Update Date
• Application > Vendor > Legal Name
• Application > Vendor > License Effective Date
• Application > Vendor > License Expiration Date
• Application > Vendor > License Number
• Application > Vendor > Modified Date
• Application > Vendor > Name
• Application > Vendor > Next Review Date
• Application > Vendor > Phone > Extension
• Application > Vendor > Phone > Host Values > Field1
• Application > Vendor > Phone > Host Values > Field2
• Application > Vendor > Phone > Host Values > Field3
• Application > Vendor > Phone > Host Values > Field4
• Application > Vendor > Phone > Host Values > Field5
• Application > Vendor > Phone > Host Values > Value
• Application > Vendor > Phone > Phone Number
• Application > Vendor > Phone > Phone Type Id
• Application > Vendor > Principal Credit Report Date
• Application > Vendor > State Code
• Application > Vendor > Termination Date
• Application > Vendor > URL
• Application > Vendor > Vendor Market Id
• Application > Vendor > Vendor Quality Scores > Quality Score Type Id
• Application > Vendor > Vendor Quality Scores > Score
• Application > Vendor > Vendor Quality Scores > Vendor Id
• Application > Vendor > Vendor Representative Id

The Pricing Model functionality has been enhanced to allow institutions to call custom code to set the interest rate on Temenos applications. Prior to this enhancement, the logic for Pricing Models was standard and set through business rules. If an institution maintained their pricing logic in an outside system, they had to recreate and maintain the logic in the rules assigned to a standard pricing model in Temenos Infinity. Now, institutions are able to define custom code in a third party system, and point to the DLL for the custom code in a Temenos Pricing Model.

To support this, a new parameter titled Pricing Model Type has been added to the General tab of the pricing model configuration window in System Management > Origination > Pricing Models to allow institutions to determine whether the pricing model being created is standard, or uses custom code. If set to Custom Code, the Base Rate and Thresholds sections are removed from the General tab, and two new parameters, Class Name and Assembly Path, are added to allow administrators to enter the information for the custom DLL being used to set the interest rate for the pricing model.

During the pricing process, when a Pricing Model is configured to execute custom code, the system bypasses the existing pricing logic, and reads the Class Name and Assembly Path configured for the model to execute the DLL and set the Interest Rate Assigned in the application.

For more information, please see the Pricing Models topic in the Administrator Guide.

Corrected an issue where the Available Decline Reasons in the Adverse Action window were not displayed in the list order defined for the REJECT_REASONS lookup in System Management > Origination > Field Configurations. Additionally, through this defect, the following lookups were also corrected to display the defined list order:

• APPROVE_AMOUNT_CHANGE_REASON